User interfaces for providing updated contact information

ABSTRACT

An Internet-based system capable of automatically maintaining contact-related information in any computer software application or digital device which stores or manages contact-related information. More particularly, the system allows users to automatically enter and maintain contact-related information in a digital address book or similar application or device (such as a wireless phone or PDA) with minimal or no manual entry of the contact-related information by the user. The system also allows contacts of the user (i.e. people who&#39;s contact information or partial contact information is present in the user&#39;s address book application) to make corrections to their contact-related information contained in the user&#39;s address book, request reciprocal contact information from the user, deny the user access to additional or corrected contact-related information and take other actions relative to managing the contact-related information which others (users) have about them.

CROSS-REFERENCE

This application is a continuation of U.S. patent application Ser. No.14/180,325, filed on Feb. 13, 2014, which is a continuation of U.S.patent application Ser. No. 14/077,178, filed on Nov. 11, 2013, now U.S.Pat. No. 8,862,618, which is a continuation of U.S. patent applicationSer. No. 13/245,728, filed on Sep. 26, 2011, now U.S. Pat. No.8,601,022, which is a continuation of U.S. patent application Ser. No.12/406,024, filed on Mar. 17, 2009, now U.S. Pat. No. 8,032,549, whichis a continuation of U.S. patent application Ser. No. 09/969,503, filedon Oct. 1, 2001, now U.S. Pat. No. 7,505,974, which claims the benefitof U.S. Provisional Patent Application No. 60/236,872, filed on Sep. 29,2000 and is a continuation-in-part of U.S. patent application Ser. No.09/249,269, filed on Feb. 12, 1999, now U.S. Pat. No. 6,883,000, each ofwhich is entirely incorporated herein by reference.

BACKGROUND

Management of business and personal contact information is a vital partof every business-person's life. People and businesses have not only adesire, but a need to stay in touch. Our contact information changesfaster than ever before, making it exceedingly difficult for ourcontacts to keep in touch with us. So, while communication has neverbeen easier, staying in touch has never been more difficult. Therecurrently exists a significant market for manufacturers, developers andretailers of software and electronic hardware products that managepersonal and business contact information. Anyone who uses email,instant messaging, a cellular/wireless phone, a PDA (Personal DigitalAssistant), PIM (Personal Information Manager) a fax machine or atelephone with a speed dial feature (for convenience we label all ofthese types of applications and devices “digital address books” or“client computers” on a client/server computer network) knows thefrustration of entering and maintaining accurate and completeinformation in these devices. Studies indicate that in excess of 30% ofthe records in a typical digital address book are inaccurate within 12months.

There exists therefore, a substantial need for a system to reduce oreliminate the labor and errors associated with the entry and maintenanceof contact-related information into a digital address book. This systemprovides a method to substantially reduce if not eliminate, for the userof the invention, the labor and errors associated with manual data entryand maintenance of contact information into a digital address book.

Systems to facilitate updating of digital address books have beendeveloped that require both parties, both the sender of an updaterequest and the addressee, to be “members” of a service provided on aserver. There exists a need for a service where only the sender is amember of the service and the update requests can be directed to anyone,particularly any digital address book that acts as a client computer ona computer network accessible to the server. This system fills thatneed. The sender needs to be a “member” only to receive the softwarethat extracts the entries from the address book, allows the sender todraft messages, attaches the messages to particular email addresses,processes the responses, and updates the address book. A benefit of thisapproach is that it makes it easy and desirable for users to promote useof the system to their contacts. The prior art systems facilitate theuser sending invitations to join the system, but recipients must joinbefore either the sender or recipient can benefit. With this system,both parties receive immediate benefit from the system even if only oneparty is a “member”.

SUMMARY

The system provides users of digital address books, wireless telephones,Personal Information Managers, and other digital applications anddevices (“digital address books”) with a more efficient, more costeffective, more accurate, and less manually intensive method forentering and updating information stored in the device. Addressees ofupdate requests need not have previously registered with the system. Thesystem:

1. extracts existing contact records (i.e. addressee records) from auser's address book, and

2. provides a mechanism for the user to create and communicate andmanage messages to addressees requesting their updated contact-relatedinformation, and

3. presents to addressees an editable electronic form displaying thecontact-related information currently present in the user's digitaladdress book, and

4. provides a mechanism whereby the addressee can edit, enter or deletecertain information displayed on the electronic form, and

5. provides a mechanism whereby the addressee can deny the user'scurrent request for updated contact-related information, and

6. provides a mechanism whereby the addressee can deny the user'scurrent request and automatically deny the user's future requests forupdated contact-related information, and

7. provides a mechanism whereby the addressee can deny the user'scurrent request and automatically deny all user's future requests forupdated contact-related information, and

8. provides a mechanism whereby the addressee can requestcontact-related information from the user, and

9. provides a mechanism whereby addressees' responses to the user'srequests are communicated back to the user, and

10. provides a mechanism whereby the system monitors, identifies andalternately processes certain types of computer files and datastructures such as computer viruses, and

11. provides a mechanism whereby the user's digital address book isautomatically updated with the addressees' responses to the user'srequests(s) for updated contact-related information, and

12. provides mechanisms whereby the user can view the current status(i.e. “update pending”, “update denied”, etc.) of his/her contacts, and

13. provides alternate mechanisms whereby users can deliver theirrequests for updated contact information to addressees.

In one aspect, the invention is a method for updating contactinformation in a network with client and server computers that involvesautomatically extracting contact information from an address book datastructure and sending the extracted contact information to a server. Theinformation that is extracted and sent includes an address. The serversends to the address a contact information update request. When a personat the addressee computer responds with updated contact information, theserver receives the updated contact information and forwards it to theoriginating computer which automatically updates its address book datastructure for the addressee. The originating client computer can be anytype of digital address book that can communicate with a server. In avariation of this method, before the extracted contact information issent to the server, some of the extracted information is presented on adisplay and the information is sent to the server only if affirmativeuser input is received in response. In a variation of this method, thesystem monitors and eliminates certain types of computer files andinformation, such as for example known computer “viruses”, from beingcommunicated to or from the client computer.

In another aspect, the invention is a method in a server on a networkwith client computers for presenting a user with a request for update ofcontact information in an editable reply form. The method involvesreceiving from a sender client computer existing contact information,including an address for an addressee, sending to the address a contactinformation update request, presenting to an addressee client computeran editable reply form containing the extracted contact information,receiving, in the editable reply form, updated contact information forthe addressee and forwarding the updated contact information to thesender client computer. In one embodiment, the contact informationupdate request is sent via email while the editable reply form ispresented from a web page and the updated contact information isreceived at the web page. In an alternative embodiment, the editablereply form is presented as part of an email message and the updatedcontact information is received via an email reply. Receivers can add ordelete addressee information that is not currently present in theaddressee data structure record in the sender's computer. In otherwords, the sender can send an update request that includes only a nameand email address, for example, and the receiver can then add a homeaddress, product descriptions, links to a web site, etc.

In another aspect, the invention is a method in a network with clientand server computers for users to block requests for updates of contactinformation. A client computer receives from a server a request forupdated contact information directed to an address that reaches theclient computer. Information about the request is presented on a displayon the client computer and, in response to user input subsequentlyreceived, the client computer sends to the server a command to block therequest and also block future requests. The server then establishes ablock tag such that no future requests for updated contact informationwill be sent to the client address from the server until the block tagis removed.

In another aspect, the invention is a method in a network with clientand server computers for a user to deny requests from a sender forupdates of contact information. A client computer receives from aserver, directed to an address that reaches the client computer, arequest for updated contact information. The request includes a senderidentifier. Information identifying a sender of the request is thenpresented on a display on the client computer. In response tosubsequently received user input, the client computer sends to theserver a command to deny the request and all future requests having thesame sender identifier. The server then establishes a deny tag such thatno future request for updated contact information having that senderidentifier will be sent to the client address from the server until thedeny tag is removed. In a variation on the method, before the clientcomputer sends the command to the server, the server provides to theclient computer a copy of existing contact information maintained in adata structure in the sender's digital address book. The existingcontact information may be presented to the client computer either inthe form of an email or as a web page that responds to a query from aweb browser program on the client computer.

In another aspect, the invention is a method in a network with clientand server computers for a user to respond to requests for an update ofcontact information with a counter-request for an update of contactinformation. When a client computer receives from a server a request forupdated contact information concerning an addressee, the client computerpresents on a display information identifying a sender of the requestwhich is generated from a sender identifier received with the request.Then, in response to user input, the client computer sends to the servera counter-request for updated contact information concerning the sender.The information identifying the sender maybe the sender identifierreceived with the request or maybe more detailed information found in alookup table using the sender identifier to find the more detailedinformation. The lookup table may be on the client computer or on aserver. Once the server receives the counter-request, it sends to theoriginal sender a request for updated contact information. In avariation of the method, the first request for updated contactinformation includes existing contact information associated with theaddressee which was extracted from a digital address book data structuremaintained by the sender. As described above, the existing contactinformation can be sent in an email or served from a web page.

In another aspect, the invention is a method in a server on a computernetwork to aggregate contact information update requests. The serverreceives from each of many client computers a contact information updaterequest for a single addressee. Each update request has a senderidentifier. The server automatically sends to the addressee a singleupdate request that includes each of the sender identifiers.

In another aspect, the invention is a method in a server in a networkedcomputer system for obtaining and providing updated contact information.When the server receives from a sender client computer a request forupdated contact information with an associated address, the server sendsto the address a request for updated contact information. The requestcan be sent by any means, including email to a client computer, email toa web-based email server, postal service, radio, television, etc. Thenthe server receives from a responding client computer a communicationresponsive to the request. The server then determines whether theresponding client computer is associated with the address and, if it is,the server receives updated contact information from the respondingclient computer and automatically transmits the information to thesender client computer. In a variation of the method, the web page alsoprovides to the responding client computer copy of existing contactinformation received by the server from the sender client computer. Thecommunication responsive to the request may be received from a webbrowser program on the responding client computer to a web page on theserver or from any network communication device, including a web-basedemail server. The updated contact information may be automaticallywritten into the sender's digital address book.

Although the embodiments described below and in the claims refer to a“server” and one or more “client” computers, it is well known in the artthat server functions can be integrated into a “client” computer suchthat a peer-to-peer architecture is implemented, one peer computerserving to another peer computer at each step.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1-A is an overall system diagram.

FIG. 1-B is a schematic diagram of a client computer of the system.

FIG. 1-C illustrates an alternate embodiment of a client computer of thesystem in the form of a portable computer.

FIG. 1-D illustrates another alternative embodiment of a client computerof the system in the form of a hand held computer.

FIG. 1-E illustrates an alternative embodiment of a client computer ofthe system in the form of a multi-user client computer incorporating aserver computer system and a multiplicity of client computers.

FIG. 1-F illustrates a file system/data structure of the clientcomputer.

FIG. 2-A is a schematic diagram of the server system of the system.

FIG. 2-B illustrates a file system/data structure of the server system.

FIG. 3-A illustrates a representative Update Request Generation (URG)form/screen. Users of the invention utilize an electronic form such asthis to format and manage requests to addressees for updated contactinformation.

FIG. 3-B illustrates a representative status screen whereby users canview the current status of update requests.

FIG. 3-C illustrates an example Validation screen

FIG. 3-D illustrates a representative Update form. Recipients of UpdateRequests utilize such an electronic form to review, edit and otherwiserespond to the sender's request for updated contact-related information.

FIG. 4 is a system level logic diagram.

FIG. 5 is a block diagram illustrative of the user registration process.

FIG. 6 is a block diagram illustrating representative client programfunctions for generating Update Requests.

FIG. 7 is a block diagram illustrating representative server programfunctions for processing and sending Update Requests.

FIG. 8 is a block diagram illustrating representative steps which areceiver/addressee might follow to process a received Update Request.

FIG. 9 is a block diagram which illustrates representative functions ofthe server system for processing Update Requests.

FIG. 10 is a block diagram which illustrates representative functions ofthe client program for processing Updated content.

DETAILED DESCRIPTION

SYSTEM ARCHITECTURE: In a representative embodiment of the system, a“mostly connected”, client-server architecture is provided, though notrequired, for the delivery of business and personal contact andcontact-related information. The representative embodiment is “mostlyconnected” because the local or “client” computer communicates with theremote or “server” computer via a “continuous” network connection. Theclient computer and the server computer may only communicate for briefperiods of time even though they are both connected to the remotenetwork (i.e. the Internet). The client program running on the clientcomputer may communicate with a sever program running on a servercomputer whenever the user of the local or client computer connects tothe remote network (i.e. the Internet) either specifically tocommunicate with the server system or to perform other functions. Such“other functions” might include, for example, shopping for goods,trading stocks, checking email, or reading an on-line version of anewspaper on the World-Wide-Web (hereinafter referred to as “the web”).The communication session between the client computer and the remotenetwork is typically, though not necessarily, a continuous networkconnection. Alternatively, the initiation of the communication sessionwith the remote network (i.e. the Internet) may be caused by manualinput from the user or the communications session may be initiatedautomatically by the client program based upon certain criteria such as,for example, a period of I/O inactivity or idleness (similar to a“screen saver” as is well known in the art) or other parameters suchthat the user is not required to manually initiate the communicationprocess.THE CLIENT COMPUTER: The user of the system uses a client computer torun the client program and to run a digital address book application andto communicate with the server system. The client program hascommunications facilities to allow client computers to connect to andcommunicate with the server program(s). Additionally the client programcontains interface programs to communicate with other programs locatedon or accessible by the client computer such as digital address bookapplications. In the representative embodiment, the client computer isremotely located with respect to the server system. Typically, there aremany users, each with a client computer executing the client program andcapable of communicating simultaneously with the server system. Hereinthe term “client” computer shall be used to represent any localcomputing device such as a hand-held “palm top” computer, laptopcomputer, desktop computer, terminal, PDA (Personal Digital Assistant),PIM (Personal Information Manager), Network computer, wirelesscommunicator (such as a cellular or satellite telephone), or amulti-user computing system, etc. which is capable of communicating witha remote or server computer via the remote network. The client computermay also, customarily (as is well known in the art), contain an outputdevice such as a CRT or LCD screen or plasma display, a manual dataentry device such as a keyboard, keypad, touch screen, voice recognitionsystem, pen stylus, or other such manual input devices as are commonlyknown in the art. The client computer may also be equipped with anautomated input device such as a bar code reader, magnetic stripereader, “smart card” reader, MICR (Magnetic Ink Character Recognition)reader, OCR (Optical Character Recognition) reader, or other suchautomated data input devices as are well known in the art. It is likelythat multiple client computers will be communicating with the serversystem simultaneously.

In the representative embodiment of the system, a client computer isused by each user and runs a client program. In an alternativeembodiment of the system, the client computer is a multi-user computingsystem. Such a multi-user client system may consist of one or multipleserver computers with multiple secondary client computers such thatmultiple users of the system can be supported by a system of clientcomputers. The client computer has a secondary memory device, such as,for example, a hard disk drive or other non-volatile memory. The clientprogram of the system is stored on the secondary memory device of theclient computer and is executed by the client computer's processor. Itwill be appreciated by one with skill in the art that the client programmight be installed on the client computer from a number of sources suchas, for example, downloaded over the Internet from a server, bundledwith software provided by a third party software manufacturer (such as aWeb browser provided by a Web browser manufacturer), manually installedfrom media such as CD ROM, etc. It will be appreciated that the clientprogram will function in substantially the same manner regardless of theinstallation source or method. The representative embodiment of thesystem provides for downloading of the client program via the Internetfor installation on the client computer.

The client computer has the capability to connect to the remote network.The client computer may connect to the remote network via a variety ofmethods such as a phone modem, wireless (cellular, satellite, microwave,infrared, radio, etc.) network, Local Area Network (LAN), Wide AreaNetwork (WAN), or any such means as necessary to communicate to a servercomputer connected directly or indirectly to the remote network (i.e.the Internet). The term “wireless” as used in an embodiment of thesystem is defined by the capability of the system to transmit digitalinformation from one device to another without use of cables.

It will be apparent to one with skill in the art that the operatingsystem for the client computer could be either a single user operatingsystem such as Microsoft DOS or Microsoft Windows or it could be amulti-tasking/multi-threaded operating system such as Unix or MicrosoftWindows NT.

It will be appreciated by one with skill in the art that although theterms “client” and “server” are used herein, the architecture of thesystem is not limited to what is known in the art as a client/servernetwork.

THE NETWORK: As used herein the term “remote network” is used todescribe any public network such as the Internet or World Wide Web orany public or private network as may be developed in the future whichprovides a similar service as the present Internet.

THE SERVER SYSTEM: The client program periodically communicates with aserver system. Used herein the term “server” computer is used todescribe any computing device that stores and runs a server program. Theserver system facilitates the collection and distribution of content toand from a multiplicity of client computers.

In the representative embodiment of the system, the server system iscomprised of a number of application servers (running applicationsoftware programs) connected to a number of database servers (runningdatabase management software). Each server computer consists of one ormultiple high speed CPU's (Central Processing Unit(s), primary memory(i.e. RAM) and secondary storage device(s) (i.e. hard disk drives). Inthe representative embodiment of the system, the server computer(s) runone of a variety of multi-tasking, multi-threaded, multi-user operatingsystems such as, for example, Microsoft Windows NT, Unix, Linux, etc.Together the application software, the database management software, theassociated server computing hardware and operating software, and thecommunications hardware and software, comprise the server system. Theapplication programs, operating system and the database managementprograms may all run on the same computing device as in a traditional“main frame” type of configuration or several, individual yetinterconnected computing devices as in a traditional “multi-tierclient-server” configuration as is well known in the art. The serversystem is coupled to the remote network (such as the Internet). Theserver system executes a (or multiple depending on the server systemconfiguration) server program(s). The server system and the clientprogram have communications facilities to allow client computers toconnect to and communicate with the server program(s) such that theserver program(s) can communicate with and exchange information with amultiplicity of client programs. It will be appreciated by one withskill in the art that the operating system for the server systemadvantageously is a multitasking/multithreaded operating system, butcould be a single tasking/single threaded operating system.

CONNECTING TO THE REMOTE NETWORK: The user causes the system toestablish an electronic (either wire or wireless) connection with theInternet (or other such remote network as described herein). Themethod(s) for establishing communication with another computer via theInternet is well known in the art. Typically, the client computer isconnected either directly via hardware Network Interface Card or viadial up phone or cable modem to a private local area network (LAN) orwide area network (WAN) which has at least one server connected to theWorld Wide Web or the Internet. Often, the private network and serverconnection to the web are provided by an Internet Service Provider or“ISP” and the user “dials” into the ISP's network via phone modem. Theclient computer also runs a program called a “web browser”. This webbrowser is used to interpret Uniform Resource Locators (as are wellknown in the art) which represent the Internet or IP addresses of othercomputers and resources connected to the web. The browser navigates theweb and facilitates communication with devices attached to the web andinterprets web pages into a form readable on the client computer. Theserver system of the system has a known IP (Internet Protocol) addresswhich is known by the client program. Once the client computer hasestablished a communication session with the remote network, then theclient program can establish a communication session with the serverprogram using the appropriate protocols of the remote network (i.e.Internet Protocol).CAUSING CONNECTION TO THE SERVER SYSTEM: In the system, the clientprogram will cause the client computer to establish an electroniccommunications session with the server system as a result of one of amultiplicity of conditions. It will be apparent to one with skill in theart that there are many ways to cause the communication connectionbetween the client computer and the server system such as, for example;by the user actively selecting a command from a menu, by running a webbrowser software, as is commonly known in the art, by the passage oftime, or by numerous other conditions. For example, in one embodiment,the user establishes a connection to the Internet for the purpose ofchecking email. Once the connection has been made to the Internet, theclient program spawns an additional process (as is well known in theart) and causes the client computer to establish a second connectionwith the server system. In another embodiment, the user enters contactinformation, such as a name and email address, into a digital addressbook application running on the client computer. Completing the entry ofcertain contact information causes the client program to establish aconnection with the server program. In yet another embodiment, theclient program monitors Input/Output activity in much the same manner asa “screen saver” (as is well known in the art) and waits for a period ofinactivity. After a preset period of time has passed without therequisite I/O activity (keyboard activity, mouse activity, printeractivity, network activity, etc.), the client program causes the clientcomputer to establish a communications session with the remote serversystem. In another embodiment, the client computer monitors the elapsedtime since the previous communication session with the server computerand when such elapsed time exceeds a defined limit, the client computerestablishes a communication session with the remote server system viathe remote network.THE USER: A first-time user registers (on a one time basis) with theserver system and provides certain contact information to the serversystem such as, for example, his/her first and last name and emailaddress, etc. and thus becomes a Registered User. The terms “RegisteredUser” and “user” are used synonymously herein. As used herein, the term“sender” is a sender of update requests and is equivalent to a user orregistered user. In the representative embodiment, a user also providescertain information to the server system relative to the manufacturerand version of address book software (Personal Information Manager,Contact Management System, etc) (i.e. ACT version 5.0, Gold Mine version4.1, Outlook 2000, etc.) in which the user would like his/her contactmanagement data stored. It will be apparent to one with skill in the artthat the client program might also automatically determine themanufacturer and version of the digital address book resident on theclient computer and automatically make the necessary adjustments tocommunicate with the address book.THE CLIENT PROGRAM: Once the user has registered with the server system,the client program is downloaded from the server system via the remotenetwork or mailed to the user and installed on the client computer. Theclient program incorporates an information database or similar datastructure and file management system for management of the clientprogram(s), files, and data. The client program is made up of amultiplicity of programs that perform certain functions. Theseprograms/functions include, but are not limited to, for example: an“INSTALLATION AGENT” to install and configure the client program(s), a“COMMUNICATION MANAGER” to manage the processes of connection andcommunication between the client computer and the server system. Theclient program also contains an “EVENT MANAGER” program which recordsand transfers (to and from the server system) all events (includingentry of contact records, attempts to alter the client program, etc.)taking place on the client computer. The client program also contains an“ADDRESS BOOK INTERFACE” which manages the transfer of informationbetween the client program and the records or other data structure ofthe user's address book application.THE DIGITAL ADDRESS BOOK: As referred to herein, an “address book” isany digital application or device that stores contact relatedinformation such as names, phone numbers, email addresses, etc. in adata structure. It will be appreciated by one with skill in the art thatthere are a multiplicity of applications and devices such as wire-lineand wireless telephones, fax machines, PDA's, email systems, CustomerRelationship Management (CRM) systems, Sales Force Automation (SFA)systems, Human Resource systems and numerous other applications anddevices that typically store and manage contact-related information.EXISTING CONTENT: Existing content, as used herein, is the existinginformation that is stored in the address book application before it hasbeen updated.UPDATED CONTENT: Updated content, as used herein, is content that hasbeen updated by a recipient/addressee.UPDATE REQUEST: An update request, as used herein, is a request by asender delivered to an addressee, typically via email, requestingupdated content.RECIPIENT: A recipient, as used herein, is any person or system thatreceives an Update Request.ADDRESSEE: An addressee, as used herein, is any person to whom an updaterequest is addressed.SENDER: A sender is equivalent to a “user” of the client program.Senders send update requests to addressees/recipients.STATUS TAG: Status tags are utilized by the system to indicate thestatus of contacts and/or update requests. For example, the recipient(addressee) of an update request has a multiplicity of options regardingresponding to the update request. For example, if the recipient does notwant to provide updated content to the sender, then the recipient canrespond by “denying” the sender's update request, in which case theaddressee's record in the user's address book will be marked with astatus flag of “denied”.Process Description

Once the client program has caused the user's client computer toestablish an electronic communication session with the server system,regardless of the process that caused the connection (i.e. manual orautomated), the client program then passes the stored update requests tothe server system. The client program also passes information containedin other files such as the log file, the statistics file, theconfiguration file and others, described in greater detail herein, tothe server system. The server system checks addressee records todetermine if a “deny” or “block” or other tag is present for arecipient. If a deny or block tag is present in the addressee's record,then the server system will not forward the update requests to theaddressee. If the addressee has received a number of update requests (asdetermined by the server program, but typically 3 requests) in a priorperiod of time (as established by the server program, but typically a 24hour period) then the server program will hold update requests for eachaddressee for which the multi-request threshold has been exceeded untilthe established threshold time period has expired (typically 24 hours).At this point the server system will bundle all update requests for anaddressee together and deliver the multiple requests in one email withall senders identified in the email.

Prior to forwarding the update requests to addressees, the serverprogram attaches text to each update request email which contains, amongother things, a URL which the recipient can use to respond to the updaterequest. An addressee receives the update request(s) (typically viaemail, but other methods are provided for in alternative embodiments ofthe system) and responds by clicking on a link (a URL) contained in orattached to the email. The server program validates that the recipientis the intended recipient and then displays an update request form (aweb page) via which the recipient can confirm, edit or add to thepresented (“existing”) content (i.e. the information which the senderhas about the addressee in the sender's address book). The recipient canalso deny the sender's request, block further requests and/or requestthat the sender provide reciprocal content (i.e. the sender provides therecipient with the sender's contact-related information). The serversystem then stores the recipient's response (i.e. updated content) untilthe next time the client program communicates with the server program.The client program communicates with the server program on a periodicbasis (typically every 24 hours) to deliver Update Requests to theserver program and to receive completed Update Requests (i.e. “UpdatedContent”) from the server program. The server program then communicatesthe Updated Content to the client program which in turn updates theuser's address book.

The server system also passes update information to the client program.Program updates (patches, bug fixes, new features, etc.) are sent to theconfiguration file. New communications parameters such as modemconfigurations, access phone numbers, device URL's, etc. are alsodownloaded to the configuration file. The information downloaded fromthe server system to the client computer is often referred to herein as“inbound information”. Once all the appropriate information (inboundinformation) has been downloaded from the server system to the clientcomputer, the server system terminates the communication session withthe client program. The client program will then cause the appropriateupdated contact content to be stored in the appropriate locations withinthe user's designated address book. The user can then use the addressbook as usual to create, edit, store, retrieve, output, and otherwisemanipulate business and personal contact information. The configuration,statistics, and ad control information are stored in their respectivefiles as well. It will be appreciated by one with skill in the art thatmany of the processes described herein can be executed as serialprocesses, as parallel processes and as background processes andcombinations thereof.

Process Overview

I. User Registration:

-   -   1. New user registers at web site    -   2. Registered user is assigned a universal user identifier        (UUID)    -   3. Client program downloaded to client computer    -   4. Client program installed on client computer        II. Preparation of Update Requests:    -   5. Client program runs and communicates with the address book        program on the client computer.    -   6. Client program extracts and displays on a request screen        identification information about the contacts represented in the        address book. Identification information may be, for example,        first and last name of the contact and company name. Optionally,        the client program may also display additional existing content        about the contact such as, for example, email address and        mailing address, etc and the client program may assemble and        display information about the contact extracted from the client        program database.        -   a. if an assembled addressee record contains a status tag of            status “denied”, then addressee information is displayed on            a status screen as “denied”.        -   b. if an assembled addressee record contains a status tag of            status “blocked”, then addressee information is displayed on            a status screen as “blocked”. A similar procedure applies to            other addressee records with status tags such as “pending”,            “undeliverable”, etc.    -   7. From a request screen, the user selects email addresses to        which update requests will be emailed.        -   a. If an addressee record is marked as “denied” or            “blocked”, then the client program will not allow the            addressee to be “selected” and no email communication will            be sent by the client program.    -   8. User selects template text to include in the update request        email.    -   9. User can edit template text or create their own message.    -   10. User associates/links email text to selected addressees        -   a. User can “reassign” an email text to a different            addressee or group of addressees or all addressees.    -   11. User causes the client program to send the update requests        to the server program.        -   a. Server program records information and statistics about            the update requests such as:            -   i. Date and time update requests sent            -   ii. Addresses to be mailed to            -   iii. Copy of the text contained in the email (update                request)            -   iv. Sender identification.            -   v. Success or failure of the email delivery        -   b. The server program checks the server database for “deny”,            “block” and other status tags on addressee records and will            not deliver update requests for those addressees with such            tags.        -   c. The server program checks the “multi-requests” threshold            for each addressee to see how many update requests have been            delivered to a recipient in a prior period of time. If the            multi-request threshold has been exceeded then the server            program will hold all further update requests for that            addressee and bundle them for delivery at a later time in            one delivery with multiple sender ID's.        -   d. If the addressee is not tagged with a “deny”, “block” or            other status tag and the multi-requests threshold has not            been exceeded, then the server system delivers the update            requests to the addressee(s).            III. Completion of Update Requests:    -   12. Addressee's computer receives the update-request email.    -   13. The email text includes a link to a web page (or other        presentation medium) which, if selected, will display to the        addressee the addressee's contact information known to the        sender—the information currently present in the user's        (sender's) address book about the recipient/addressee (we will        call this “existing content”).    -   14. The recipient opens the email (using any of a multiplicity        of standard email clients) containing the update request.        -   a. The email is addressed from the sender for identification            purposes.        -   b. The email may be sent to the addressee directly from the            client computer or via the server system.    -   15. Recipient (addressee) clicks on the link (or copies the URL        into his/her web browser) present in the email text and is        presented with a “validation page” which is a web page (or other        presentation media) displaying identifying information (such as        name and email address) of the intended recipient (addressee).        The validation form allows the recipient to confirm that he/she        is in fact the intended recipient.        -   a. If recipient is not the intended recipient and is a            registered user of the system, then the recipient is            presented with an update page containing an update form with            no existing content presented.        -   b. If recipient is the intended recipient, then recipient is            presented with an update page with existing content            presented in the update form. The update page may include            instructions and links to other web pages.        -   c. Intended recipient can:            -   i. edit existing content,            -   ii. request reciprocal content,            -   iii. deny the sender's request,            -   iv. block further requests,

If “i”, then:

-   -   a. Recipient makes any necessary changes to existing content.    -   b. Recipient indicates when he/she is finished (having edited        the existing content or approving the existing content “as is”).    -   c. New/changed information about the recipient (updated content)        is recorded by the server program.    -   d. The server program prepares and sends a notice of pending        update to sender.    -   e. The sender's client program establishes a communication        session with the server system.    -   f. The updated content is communicated to the sender's client        program.    -   g. Client program updates records in the sender's address book        with the updated content.    -   h. Client program date and time stamps the updated content.

If “ii”, then:

-   -   a. if the addressee is a registered user, then, after the        addressee has completed performing updates for the current        update session, the server program sends an update request        addressed from the addressee to the sender of the current update        request.    -   b. If the addressee is not a registered user, then, after the        addressee has completed performing updates for the current        update session, the server program leads the addressee through        the registration process before sending an update request from        the addressee to the sender of the current update request.

If “iii”, then:

-   -   a. The server program records a “deny” entry for that particular        recipient for that particular sender.    -   b. At the next client program-to-server program communication        session, the client program will tag the addressee as “denied”        for the sender so that the client program will not allow this        sender to send an update request to this addressee at a later        time. The “deny” entry is recorded in the user's address book        and in the server program.    -   c. The client program does not update the sender's address book        with updated content for this addressee/recipient.

If “iv”, then:

-   -   a. The server program records a “block” entry for that        particular recipient for all senders. The server system will not        deliver any update requests to a recipient with a block tag        regardless of identity of the sender.    -   b. At the next client program-to-server program communication        session, the client program will tag the addressee as “blocked”        for all senders so that the client program will not allow this        sender to send an update request to this addressee at a later        time. The “blocked” entry is recorded in the user's address book        or client program database and in the server program database.    -   c. The client program does not update the sender's address book        with updated content for this addressee/recipient.        System Components:        FIG. 1-A illustrates an exemplary configuration of the system.        The representative embodiment is illustrative of an Internet or        World-Wide-Web based automated Contact Information Updating        system.        As shown in FIG. 1-F, the representative embodiment of the        system provides for a computer based system that allows users of        digital address-book applications 170 and/or client computing        devices 100 such as, for example, computers, cellular        telephones, wireless telephones, Personal Information Managers,        etc. which store contact-related information 172 to        automatically update the contents of the application 170 or        client computing device 100 with updated content 174 by        delivering by electronic means an Update Request Form (FIG. 3-A)        to addressees as identified from the user's address book        170—whereby addressees view and/or edit the existing content 172        whereupon the user's address book application 170 or device 100        is then updated with updated content 174.        CLIENT COMPUTER: The client computer 100 is typically a personal        computer as illustrated in FIG. 1-B, but may also be a        multi-user computing system as illustrated in FIG. 1-E such as,        for example, a client server system communicating with        supplemental client computers 115 via a private network or via        the Internet or other such network or a web server communicating        with supplemental client computers 115 via the world wide web.        Alternatively, the client computer 100 may be a portable        computer such as a laptop or notebook computer as illustrated in        FIG. 1-C or a wireless communicator or hand held device such as        a cellular or wireless telephone, or PDA (i.e. 3-com's Palm        Pilot) as indicated in FIG. 1-D. It will be appreciated by one        with skill in the art that client computers 100 and supplemental        client computers 115 could, alternatively, be configured in many        different configurations suitable to varying technologies. It is        common for users of client computers 100 (particularly portable        or hand held computing devices to maintain information on a        multiplicity of client computers. It is often desirable for the        user of such multiple client computers 100 to synchronize or        replicate the information contained on each of the multiple        client computers such that all of the user's multiple client        computers contain the same information. It may also be desirable        that the user's multiple client computers 100 contain different        sets of information such as, for example, personal        contact-related information on one or multiple client computers        and business contact-related information on different client        computers and/or a subset of contact-related information such        as, for example, names and phone numbers only on a wireless        telephone, etc. Accordingly the system provides for utilization        of a multiplicity of client computers 100 by a single user and        multiple supplemental client computer(s) 115. Although the        representative embodiment of the system discusses the use of one        client computer(s), it will be appreciated by one with skill in        the art that a supplemental client computer 115 may also be        utilized to send and receive information directly to and from        the server system. Alternatively, supplemental client computers        115 may send/receive information indirectly to/from the server        system 130 via the client computer 100 as illustrated in FIG.        1-A. Client computers 100 may be configured as multi-user client        computing systems FIG. 1-E such as Internet, Intranet or Web        systems as commonly known in the art.

As illustrated in FIG. 1-B, the client computer 100 includes a centralprocessing unit (CPU) 108 to execute programs (including the clientprogram) and manage the operation of the client computer 100. Primarymemory 110 (i.e. high speed random access memory) is coupled to the CPU108 and is used for temporary storage of programs and data, and asecondary memory device 104 (i.e. disk or optical storage) coupled tothe CPU 108 is used for non-volatile storage of programs and data. Aremovable media storage 106 (i.e. floppy disk or CD ROM or optical disk)is coupled to the central processing unit 108 for purposes of loadingcomputer programs, including the client program, and data into theclient computer 100 and for non-volatile storage of computer programsand data. Output device 102 (i.e. CRT or LCD panel) is also coupled tothe CPU 108 and provides a user interface, and manual input devices 113,114 and 116 such as audio input microphone, key board and mouse andautomated input device(s), such as a bar code reader 118 or magneticstripe reader(s) 117, coupled to the CPU 108 provide means for a user ofthe client computer 100 to input commands, data, etc. Other inputdevices such as, for example, touch screen, voice recognition with amicrophone 113 for input, Optical Character Recognition, Smart Cardreader, etc. are examples of alternative input devices for alternativeembodiments of the system. A communications interface(s) 112 such as aphone modem or network interface card (NIC) is coupled to the CPU andprovides a means for the client computer 100 to communicate with theserver system 130 and other computers via the remote network 120.

Although FIG. 1-A illustrates only 1 client computer 100 communicatingwith the server system 130, it is understood that the system is intendedto support a plurality of client computers 100 (of a multiplicity ofconfigurations) communicating with the server system 130 simultaneously.It will be appreciated by one with skill in the art that the type ofcomputing device which comprises the client computer 100 and the type ofdevice which comprises the communications interface 112 may be a varietyof different devices and configurations and technologies and may bephysically packaged as one or many distinct entities. For example, asillustrated in FIG. 1-C, the client computer 100 may consist of a laptopor notebook computer 113 (as is well known in the art) with a built-in,wireless modem which communicates to the remote network 120 via asupplemental digital or analog cellular, satellite, radio, or other suchdigital or analog communications network. Or, as illustrated in FIG.1-D, the client computer 100 might consist of a hand-held PersonalDigital Assistant (PDA) 103 or wireless telephone and communicate via abuilt-in cellular or satellite communications interface 112 to theremote network 120 via a satellite-based or cellular or radio basedcommunication system. The spirit of the representative embodiment of thesystem is to provide for a client computer 100 that is capable ofproviding adequate processing power and storage for programs and/or dataand which will communicate with a remote server system 130 via a remotenetwork 120. As illustrated in FIG. 1-E, it is desirable andadvantageous that the client computer 100 be a multi-user system capableof supporting a multiplicity of users via supplemental client computers115. The communications interface 112 might, alternatively, be a networkinterface card (NIC) which communicates with a Local Area Network (LAN)or Wide Area Network (WAN), or the like, communicating via TCP/IP orX.25 or other such network protocols, which in turn communicates with oris coupled to the remote network 120. Alternatively, it is alsodesirable and advantageous that the client computer 100 be highly mobile(i.e. battery powered, hand-held, etc.) and capable of wirelesscommunication with the server system 130.

THE REMOTE NETWORK: The client computer 100 is located remotely from theserver system 130 and communicates periodically with the server system130 via the remote network 120. Alternatively, the client computer 100communicates via a dedicated connection to the remote network 120 suchthat the client computer 100 can communicate with the remote network 120at any time without having to establish a new communication session withthe remote network. In the representative embodiment of the system, theremote network 120 is the Internet or World Wide Web (herein referred toas “the web”), but it will be appreciated that the network may be anysuch communications network, either public or private or a combination,which provides computer-to-computer communications between a pluralityof client computers 100 and the server system 130. While FIG. 1-Aillustrates one client computer 100 communicating with the server system130, it is understood that the system provides for many client computers(in any multitude of configurations) to communicate simultaneously withthe server system. A communication session is established between theclient computer and the server system 130 by causing the client computercommunications interface 112 to establish an electronic dialog with theserver system's communications interface 132 via the remote network 120(i.e. the world wide web or the Internet).THE SERVER SYSTEM: As shown in FIG. 2-A, the server system 130 iscoupled to one or more remote networks 120 via one or morecommunications interface devices 132 and one or more communicationsservers 136. The server system 130 receives, stores, transmits andotherwise manages update requests (FIG. 3). As shown in FIG. 2-B, theserver system 130 also receives, stores and transmits other informationto and from client computers 100 such as statistics 264.10, log files264.4, event logs 264.8 and other such information that is advantageousto the proper operation of the system as described herein.

The representative embodiment of the system provides for a multi-tierarchitecture for the server system 130. As such, server system 130 iscomprised of a plurality of high performance servers 134-137 coupledtogether via a high-speed network 138. The representative embodiment ofthe system provides for a plurality of application servers 134, aplurality of database servers 135, a plurality of communications servers136, and a plurality of subscription and registration servers 137. Itwill be appreciated by one with skill in the art, however, that Serversystem 130 could, alternatively, be configured in many differentconfigurations suitable to varying technologies. For example, analternative configuration might consist of one or multiple largeserver(s) performing multiple functions as in a traditional “main frame”configuration. Alternatively, the individual servers 134-137 of serversystem 130 could perform multiple functions such as application serverand registration server in one physical entity. It is also understoodthat the devices which comprise server system 130 may be located ingeographically dispersed locations or may all reside in one physicallocation.

SERVER COMPUTERS: The representative embodiment of the system providesfor one or more registration servers 137 which accommodate first timeusers in registering to (as described herein) the server system 130.Database servers 135 support (i.e. execute programs and store data,accept inputs and produce outputs, etc.) the database management system264 of the server system 130. Application servers 134 execute and storethe application programs of the server system 130. Communicationsservers 136 provide communications connectivity between the serversystem 130 and client computers 100 via the remote network 120.

The individual servers 134-137 of server system 130 each, typically,contain the following components: one or more high speed CPU's, primarymemory (i.e. high speed RAM), one or more secondary storage devices(i.e. high capacity hard disk drive(s)), removable media drives (such asCD ROM or tape) for loading and storage of programs and data, and one ormore network interface card(s) or other such means to interface to thelocal high speed network 138. Additionally, connected to the localhigh-speed network 138, are a plurality of network devices such as highcapacity, high-speed secondary storage devices 144 (such as hard diskdrives), backup/archive devices 140 and 141 such as tape drives and/oroptical disk drives for high capacity, high-speed loading of programsand data as well as archiving and backup of programs and data. One ormore consoles 145 (or other such user interface devices such as a CRT),and keyboard 146 and mouse 147 are also provided for user control of theserver system. The local network 138 is a high-speed, high-capacityEthernet or other such-high speed, high-capacity network as to providehigh-speed, high bandwidth computer-to-computer communications.

CONNECTION TO THE SERVER SYSTEM: Referring to FIG. 1-F, client program150, based on one or more of a multitude of conditions, causes theclient computer 100 to establish a communications session with theserver system 130 via remote network 120. The client computer 100contains a web browser (such as, for example, Microsoft InternetExplorer or Netscape Navigator) or other such Internet or remote networknavigation technology and a communications interface 112 to facilitatecommunications via the remote network 120 to other computers capable ofcommunicating via the remote network 120 and specifically, the serversystem 130.

The client program 150 is delivered to the user and installed on theuser's client computer 100 with the pre-established URL of the serversystem 130. The client program automatically passes the pre establishedURL of the server system 130 to the web browser (or other suchnavigation and communication program) of the client computer 100 andcauses the client computer 100 to establish a communications session viaremote network 120 to the server system 130. It will be apparent to onewith skill in the art that there are numerous methods by which theclient computer 100 might initiate the communication connection betweenthe client computer 100 and the server system 130. One suchcommunication initiation method might be, for example, the user activelyselecting a command from a menu such as “update contacts”. Anothercommunication initiation method might be, for example, the clientprogram 150 causing the web browser (or operating system 101) of theclient computer 100 to spawn an additional Internet connection while theclient computer 100 is already communicating via the Internet andsimultaneously performing other tasks. Yet additional initiation methodsmight be, for example, by the passage of time, by lack of inputactivity, or by numerous other conditions.

For example, in one embodiment, the user establishes a connection to theInternet (remote network 120) for the purpose of checking email. Oncethe connection has been established between the client computer 100 andthe Internet (or World Wide Web), the client program 150 spawns (orcauses the operating system, web browser or other such program of theclient computer 100 to spawn) an additional process/connection (as iswell known in the art) to the remote network 120 and causes the webbrowser or other such program of the client computer 100 to establish asecond communication session simultaneous with the first communicationsession, the second communication session being a communication sessionbetween the client computer 100 and the server system 130.

In yet another embodiment, the client program 150 monitors Input/Outputactivity in much the same manner as a “screen saver” (as is well knownin the art) might and waits for a period of inactivity. After a presetperiod of time has passed without the requisite I/O activity (keyboardactivity, mouse activity, printer activity, network activity, etc.), theclient program 150 automatically causes the client computer 100 toestablish a communications session with the remote server system 130.

It will be appreciated by one with skill in the art that other automated“house keeping” tasks such as, for example, validating data, processingand reporting of errors, logging events, collecting statistics, etc. arealso conducted by the client and server systems when communicatingand/or transferring inbound and outbound information.

The preferred embodiment of the system may also, though not necessarily,execute processes (whether concurrent or sequential) as backgroundprocesses to other processes taking place concurrently on both or eitherthe client computer and/or the server system. It will also be obvious toone with skill in the art that the relative timing and sequence of thevarious functions performed by the client and server programs can bemodified without altering the spirit or functionality of the system.

System Logic Overview:

For clarity, the movement of information (programs, files, data, etc.)between the client computer 100 and the server system 130 can bedescribed from the perspective of the client computer. Information whichis transferred (often referred to herein as “uploaded”) from the clientcomputer to the server system is often referred to herein as “outbound”information (programs, files, data, or other such digital information).Information which is transferred from the server system to the clientcomputer (often referred to herein as “downloaded”) is often referred toherein as “inbound” information.

FIG. 4 illustrates the basic processes of a representative embodiment ofthe system.

Step 402: A first-time user of the system registers with the serversystem and becomes a registered user (herein referred to as a user).

Step 405: The client program is downloaded via the remote network 120and automatically installs on the client computer 100. Alternatively theclient program is delivered by other means such as a CD ROM deliveredvia mail. Alternatively the client program is installed manually.

Step 410: The client program runs on the client computer. The clientprogram can be run automatically based on a calendar schedule or otherinputs. Alternatively a user can launch the client program by executinga command.

Step 415: The client program communicates with a digital address book onthe client computer and identifies potential addressees.

Step 420: The client program 150 generates an Update Request Generationform as shown in FIG. 3-A which displays eligible addressees 308 andsample update request text (email text) 344 which can be edited andlinked to selected addressees.

Step 425: Once the update request email contents have been linked to theselected addressees 308 the client program communicates with the serverprogram and sends the update requests to the server system 130 via theremote network 120. Update requests include existing content. The clientprogram 150 also communicates additional “outbound” information to theserver system 130 such as, for example, with reference to FIG. 2-B,statistics for storing in a statistics data structure 264.10 on theserver and log files for storing in a log files data structure 264.4 onthe server.

Step 430: Upon receipt at the server, with reference to FIG. 2-B, theserver program 250 stores a copy of the existing content in an existingcontent data structure 172 and a copy of the update request emails in anupdate requests master data structure 261 associated with eachaddressee. The server program 250 records the additional outboundinformation in the appropriate data structure (statistics 264.10 and logfiles 264.4, etc.).

Step 435: The server program 250 forwards the update requestnotifications to the addressees. As shown in FIG. 3-D which shows ascreen display presented to an addressee, each Update RequestNotification contains one or more requester identifiers 364, 370 and376. The Update Request Notifications (notifications) are typicallydelivered to addressees via email. If the server program determines thata notification cannot be successfully delivered via email then theserver program may attempt alternative methods of delivery such as, forexample, fax, voice, or paper mail, as is well known in the art.Alternatively, the server program may attempt to locate a valid contactinformation for the addressee by automatically searching publicdirectories such as, for example, “white pages” directories, as is wellknown in the art, available via the World Wide Web or by searching otherpublic or private directories as may be accessible to the sever program.

Step 440: Addressee(s) respond to Update Request Notifications. UpdateRequest Notifications contain an Update Request Notification Link whichis a world wide web URL—Universal Resource Locator, as known in the art.The Update Request Notification Link 346 was presented to the sender aspart of the draft notification text as shown in FIG. 3-A. The UpdateRequest Notification Link 346 is “linked” to the Addressee ValidationForm as shown in FIG. 3-C. If the notification is delivered via email,then the addressee can activate the link 346 by clicking on it, as iscommonly known in the art, or by entering the link in the URL field of aweb browser. If the notification is delivered to the addressee viaalternative methods, then the addressee can view the AddresseeValidation Form shown in FIG. 3-B by entering the link into the URLfield of a web browser.

Step 442: Addressee is presented with the Addressee Validation Formshown in FIG. 3-C. If the recipient responds that the update request issomeone other than the addressee by clicking the NO button 397, then anEvent Trigger is activated. An Event Trigger can cause a multiplicity ofactions such as, for example, presenting the recipient with an alternateweb page, recording statistics about the event, etc.

Step 445: If the recipient confirms that they are the intended recipient(the addressee) by clicking the YES button 396, then they are presentedwith the Update Form shown in FIG. 3-D with existing content displayedin the update form.

Step 450: The addressee can elect to update the existing content byselecting the appropriate elements/sub-elements and entering the desiredinformation. Alternatively, the addressee can take a multiplicity ofalternate actions such as, for example:

-   -   a. Deny the update request.    -   b. Block further update requests.    -   c. Confirm the existing content.

Step 455: Once the addressee indicates that they have completed theirupdate activities, the recipient's browser program sends the update tothe server and the server program 250 communicates the now updatedcontent to the sender's client program 150 during a subsequentcommunication session between the client program and the server program.The server program also records and communicates other information tothe sender's client program such as, for example, Status Tags from theTags master file data structure 255.

Step 460: As shown in FIG. 1-F, the client program 150 updates thesender's address book 170 by recording the updated content in theupdated content data structure 174 and the appropriate status tags inthe status tags data structure 160.2.

System Logic Detail

Steps 505 & 510: Establishing a Registered User Account:

Beginning at step 505 in FIG. 5, referring to FIGS. 2-A and 2-B, afirst-time user of the system establishes communication with aRegistration Manager 252 running on a Registration Sever(s) 137 forpurposes of establishing a Registered User Account (herein oftenreferred to simply as a “user”). The registration manager 252 presentsthe first-time user with a “Registration” screen. The first-time usercreates a Registered User account, step 510. Certain information isrequired to establish a Registered User account and some information isoptional. User account information may include, for example, name,company name, title, phone number, email address, etc.

Steps 515 & 520: Assign and Attach UUID:

Once the user has entered the required registration information they areconsidered a registered user (referred to herein as simply a “user”).The registration manager 252 creates a user account file containingregistration information 264.6 and causes the UUID generator 254 toautomatically generate a unique Universal alpha-numeric User Identifier(UUID) (step 515). The registration manager then assigns the UUID to theclient program and assigns the same UUID to the user account file. AUUID is a unique identifier used by the server program 250 to identifyeach individual client program 150 and each user when the client programcommunicates with the server program. If the client program 150 isdownloaded from the server system 130 via the remote network 120 thenthe server system assigns the UUID to the user at the time the userregisters and the server system 130 downloads the client program 150 tothe user's client computer 100. If the client program 150 is received bythe user by means other than downloading via the remote network 120 thenthe UUID assigned to the client program is not associated with the useruntil such time as the first-time the user establishes a communicationsession with the server system 130 and registers as described above.

Step 525: Download Client Program:

The server program 250 downloads the client program 150, step 525, tothe user's client computer 100 and terminates the communication sessionbetween the user client computer 100 and the server system 130. Thepreferred embodiment of the system depicts an “always on” (i.e.constant) communication session between the client computer 100 and theremote network 120. For purposes of clarity and to address alternativeembodiments, this document describes an embodiment which supportsperiodic communication sessions between the client computer 100 and theserver system 130. It will be appreciated by one with skill in the artthat it may be beneficial for the server system 130 to down load aclient program 150 which is capable of operating on a variety of clientcomputer operating systems 101 and of communicating with a wide varietyof address books 170 (i.e. Act, Gold Mine, Outlook, Palm Pilot, Nokia,Motorola, etc.). Conversely, in the interest of efficiency, it may bebeneficial for the user to select (or the server system to automaticallyassign), while on line with the server system, a client program 150which is optimized specifically for one or a subset of operatingplatforms and is capable of communicating with just one or a subset ofthe possible address books 170 available. It will be appreciated by onewith skill in the art that there are a multitude of viable methods forinstalling and configuring the client program 150 on the user's clientcomputer such as, for example, downloading the client program 150 overthe remote network 120 and automatically installing the client program150 on the client computer 100 using an installation and configurationagent 152 (FIG. 1-F) or manually installing the client program 150 froma floppy disk, CD ROM, tape, DVD, etc. with the assistance of aninstallation and configuration script or wizard 152 (as is well known inthe art). An installation and configuration agent 152 might, forexample, accompany the client program 150 which could automaticallyconfigure and install the client program 150 on the client computer 100.The representative embodiment of the system provides for the automaticdelivery, installation and configuration of the client program 150 viaremote network 120 and an installation agent 152 and is but one exampleof how the client program 150 delivery, installation and configurationmight be accomplished.

Step 530: Install Client Program

The client program 150 must be installed on the client computer 100 andproperly configured before the registered user can operate the clientprogram 150. The client program 150 includes a setupprogram/installation agent (or script) 152 which will determine if thereis sufficient space on the storage device 104 (FIG. 1-B) of the clientcomputer 100 on which to install the client program 150. When run, thesetup program/installation agent 152 automatically creates the necessarydirectory(s), sub-directories, icon(s), etc. on the client computer 100.The installation agent typically automatically identifies clientcomputer resources (such as drive and path names, modem configuration,CMS/PIM manufacturer and version, etc.) and automatically installs theclient program. Alternatively, the installation script may prompt theuser for information to assist in the installation such as modem typeand speed, phone dialing procedures (i.e. access to outside dial tone),directory paths, address book information, optional functions, etc. Theinstallation agent 152 then installs and stores the client program 150and it's associated files and executable programs in the directory(s)and it's associated sub-directories. For example, the directory createdby the installation agent/setup program might be labeled “Webbcard”. Theinstallation script/agent then creates a plurality of sub-directories(as are well known by one with skill in the art) such as, for example, a“Webbcard.bin” sub-directory for executable program(s) and associatedDLL's, a “Webbcard.tmp” sub-directory for temporary files, etc. Theinstallation agent might also create additional sub-directories forutilization by the client program at a later time. The installation andconfiguration agent 152 also creates other files necessary for theproper functioning of the client program such as, for example, a “statustags” file 160.2 (FIG. 1-F) for storage of update request status tags,an “event log” file 156.2 for tracking the performance of the clientcomputer (i.e. errors, file corruption, communication statistics, etc.),etc. Examples of files created under the “inbound” sub-directory mightinclude, for example, an “inbound spooler” file 155 for temporarystorage of inbound updated content prior to transfer to the user'saddress book 170, a “configuration” file 153 which describes UniversalResource Locators, Internet Protocol (IP) addresses, and otherparameters necessary for the client computer 100 to communicate with theserver system 130. The setup program/installation agent 152 alsodetermines if a previous version of the client program 150 has beeninstalled and if updating of the previous version to a newer version isrequired. The system does not require that the entire client program 150be installed all at once. The representative embodiment of the systemallows for the client program 150 to be installed in sections.

Generating Update Requests (FIG. 6)

Step 605: The client program 150 runs on the client computer. Therepresentative embodiment of the system depicts the client program 150running on a multi-tasking client computer operating system 101, as iscommonly known in the art, such that the client program 150 will runsimultaneously with other programs 162 running on the client computer100. Advantageously, the client computer operating system 101 would alsobe multi-threaded as is commonly known in the art. Also advantageously,the client computer operating system 101 would also be a multi-useroperating system capable of supporting multiple supplemental clientcomputers 115 and multiple users. Also advantageously, the clientcomputer operating system 101 would provide a graphical user interface,as is commonly known in the art. The program 150 is launchedautomatically upon startup of the client computer 100. Alternatively theclient program 150 can be launched via manual command according to theprocedures of the client computer operating system 101. Alternatively,and advantageously, the client program is launched (as commonly known inthe art) based upon conditional inputs caused by other events such as,for example, the launching of other programs such as the address bookprogram(s) 170 with which the client program communicates.

Step 610: The client program 150 communicates with the address bookprogram(s) 170 via address book interface 160. Address book interface160 supports a wide variety of communication protocols, data formats,etc. such that the client program 150 is capable of communicating with awide variety of address book applications, cellular and wirelesstelephones, Persona Digital Assistants, Contact Management Systems,multi-user Customer Relationship Management applications, etc.

Step 615: The generation of Update Requests is typically a periodicactivity. When the user desires to generate one or more update requests,the user launches the Update Request Generation process by executing acommand. The command which launches the update request generationprocess can be executed from a menu item 312 (FIG. 3-A) from within theclient program 150 or the process can be launched via a command fromwithin the address book application 170. Upon execution of theappropriate command, the client program 150 accesses Existing Contentfiles 172 within the address book application 170.

Step 620: The client program 150 then displays the Update RequestGeneration Form (FIG. 3-A) and displays addressee identificationinformation 308 for “eligible” addressees within the Send To list 304.The client program 150 considers an addressee as “eligible” as long asthe status tag 160.2 (FIG. 1-F) associated with the addressee's record171 does not indicate that the addressee is “ineligible”. The clientprogram 150 considers an addressee ineligible if the status tag 160.2indicates an ineligible status such as, for example, a status of“denied”, “blocked”, “pending”, “undeliverable” or other such ineligiblestatus. Status tags 160.2 are stored in the client program 150 or withinthe user's address book 170 or both depending on the capabilities of thespecific address book. Copies of status tags 160.2 are also maintainedin the Tags Master file 255 in the server program. Status tags 160.2indicate the specific eligibility status of a sender's contact(s)(addressees/recipients). A status tag 160.2 of status “denied” indicatesthat the addressee/recipient has previously received an update requestfrom the user (sender) and has denied the sender's request for updatedcontent 174. A status tag 160.2 of status “blocked” indicates that theaddressee has previously received an update request from any user of thesystem (including, but not necessarily, the sender) and has elected toreceive no additional requests from any users of the system. A statustag of status “pending” indicates that the user has previously sent anupdate request to the addressee and the addressee has not yet respondedand the “no-response threshold” (step 745) has not been exceeded. Astatus tag of status “no response” (set at step 750) indicates that theaddressee has not responded to the sender's update request prior toexpiration of the response threshold clock 176 (FIG. 2-B) for thatrequest. The no-response threshold (step 745) is determined by theresponse threshold clock 176. The response threshold clock is a timingfunction present in the server program 250. The threshold response clockis activated (started) (step 732) for each update request for eachaddressee each time an update request notification is sent to anaddressee. The response threshold clock 176 is infinitely adjustablesuch that any response threshold time duration can be achieved. Thethreshold time duration is the time that elapses between the time theresponse threshold clock 176 is started (step 732) and the time it isreset (step 757 or step 980). A status tag of status “undeliverable”indicates that the email manager 260 (FIG. 2-B) was unable to properlydeliver the update request notification (email). Email manager 260manages the delivery of and responses to update request notifications.

Steps 625 & 630: Addressee records 171 which have a status tag 160.2 of“denied” are displayed (step 630) on the Status screen FIG. 3-B in thedenied list 380.

Steps 635 & 640: Addressee records 171 which have a status tag 160.2 of“blocked” are displayed (step 640) on the Status screen FIG. 3-B in theblocked list 382.

Steps 645 & 650: Addressee records 171 which have a status tag 160.2 of“pending” are displayed (step 650) on the Status screen FIG. 3-B in thepending list 384.

Steps 655 & 660: Addressee records 171 which have a status tag 160.2 of“undeliverable” are displayed (step 660) on the Status screen FIG. 3-Bin the undeliverable list 386.

Steps 670 & 675: Addressee records 171 which have a status tag 160.2 of“no response” are displayed (steps 675 and 680) on the Update RequestGeneration form (FIG. 3-A) in the send to list 304.

The Status screen (FIG. 3-B) provides the user with the status of UpdateRequests and lists of currently ineligible contacts.

Update Request Notifications:

The process of generating update requests involves the user of theclient program sending emails to his/her contacts requesting that theyupdate their information in the requestor's address book. The preferredembodiment of the system provides for an automated, batch-oriented (asis well known in the art) process of selecting eligible addressees froma list of eligible addressees and “attaching” email text to the selectedeligible addressees. It will be appreciated by one with skill in the artthat there are a multiplicity of alternate methods and technologies thatcould be utilized to facilitate the generation of update requests. Thepreferred embodiment of the system allows for support of multiplelanguages such as, for example, Japanese, German, French, Spanish,Arabic, etc. and associated character sets.

Steps 682 through 692: Update Request Generation Form (FIG. 3-A)consists of 4 primary elements: instructions 310, active Update Requestemail form 314, additional Update Request email form 342 and Send-Tolist 304. Each primary element of Update Request Generation From (FIG.3-A) consists of a multiplicity of secondary or sub-elements.

The Update Request Generation form (referred to herein as the “URG”form) contains a text element 310 which displays instructions to theuser on how to use the URG form. URG form (FIG. 3-A) contains an UpdateRequest Notification text 344 (often referred to herein as UpdateRequest Notification text or Notification text). The preferredembodiment of the system provides for an email-based Update RequestNotification text 344 in which the Update Request Notification is anemail which is delivered to the addressee via electronic mail (email) asis well known in the art. Alternatively, Update Request Notificationtext 344 may be delivered via alternate methods such as voice, instantmessaging (as known in the art), postal service, or other such alternatedelivery methods. The preferred embodiment of the system provides foralternate delivery methods for Update Request Notifications foraddressees with a status tag 160.2 of status “undeliverable”. Usersactivate one Update Request Notification email form 314 (FIG. 3-A) byselecting or “clicking on” (as well known in the art) button element348/328. Activating button element 348 changes the text displayed on thebutton, for example, from “Activate this email” to “This is thecurrently active email”. Activating a different email causes that emailto become “currently active”. Only one email is “active” at a time.Display element 328 is a textual display element used to indicate whichUpdate Request Notification email 314 is currently “active”. Displayelement 317 is a visual display element used to indicate which UpdateRequest Notification email 314 is currently active. Visual displayelement 317 might be, for example, an additional color element, anadditional shading element, or a combination thereof which visually“highlights” the currently active Update Request Notification email form314.

Update Request Notification email form 314 contains several elements.The currently active URN email form allows the user to select from amultiplicity of pre-configured or “template” email texts by activatingmenu element 332. The selected template email text is displayed as theUpdate Request Notification text 344. Users can edit the URN text 344 tosuit their specific needs by using text editor 157 or they can proceedwith the selected template text as presented. Menu element 320 providesthe user with a multiplicity of predefined or template customary (ascustomary for the user's choice of language) greetings such as, forexample, “Hello”, “Greetings”, “Hi”, “Dear”, etc. Alternatively the usercan create their own custom greeting using text editor 157. Menu element330 allows the user to select from a multiplicity of salutations for thecurrently active URN email such as, for example; first name only, firstname followed by last name, “Mr.”/“Miss.”/“Mrs.” followed by last name,etc. Alternatively, the system allows the user to create customsalutations using text editor 157. Element 334 can be activated ordeactivated by selecting it. Activating element 334 will cause emailmanager 260 to send to the user's email address, create and store, exactcopies of the each URN email sent to each addressee or group ofaddressees. Users of the system can open (i.e. display within the UpdateRequest Generation screen FIG. 3-A) multiple additional URN email forms342 by selecting the “open another email” button element 350. AdditionalURN email forms 342 are displayed on the URG form screen below theprevious URN email form and can be positioned on the screen bymanipulating slide element 338. As each URN email is activated, it isidentified by textual element 316 such as, for example, numbers orletters which increase sequentially as each new URN email form isopened. Additionally each URN email is also, advantageously, color-codedwith visual element 340. Visual element 340 assists the user in matchingURN emails with appropriate eligible addressees 308.

Users of the system select eligible addressees from a list 304 ofeligible addressees by selecting or clicking on the desired addressee'sidentifying element 308. As each eligible addressee is selected, theidentifying element 308 corresponding to the selected addressee is codedto correspond with the URN email 314 active at the time the addressee isselected. The representative embodiment of the system provides forcoding of the addressee-identifying element 308 and the URN email byboth textual identifiers (element 302) which corresponds to URN emailtextual identifier element 316, as well as color-coding via visualidentifier elements 340. Thus, for example, all addressees selected fromlist 304 while URN email “1” (as identified by textual element 316) isactive will be coded with a “1” in element 302. Additionally, asaddressees are selected from send-to list 304, identifying element 308for the selected addressee is color-coded to correspond to the visualidentifying element 340 (color element) of the then currently active URNemail. Thus, for example, a user may open 3 URN email forms. URN email“1” text may be worded appropriately to send to “personal” acquaintancesand is color code green, email “2” may be worded for “customers” and iscolor coded yellow, and email “3” may be worded appropriately for“vendors” and is color coded blue, and so on. Users can view additionaladdressees by activating slide element 336. The user can select alladdressees by activating button element 306. As each addressee isselected, the corresponding identifying information such as, forexample, first and last name and email address, is displayedadditionally in display element 324. Display element 324 expands todisplay a multiplicity of addressees simultaneously. Users can reassignaddressees to different URN emails by activating a URN email 314 oradditional URN email 342 and selecting addressees which they desire toreassign to the currently active email. Display element 326, displaysidentifying information of the sender (user of the system) such as, forexample, first name and last name and email address. Display element 322displays the subject of the URN email which the user can edit usingeditor 157. Element 346 is a text element which the client program 150adds to each and every outbound URN email prior to sending the URNemails 314 to the server program. Text element 346 contains a URL (i.e.world wide web address) which recipients of the URN email will utilizeto view the update form (FIG. 3-D). Text element 346 is not editable bythe user.

Steps 690 & 692: Once the user has completed the process of selectingand editing URN email forms and attaching addressees, etc. (steps682-688) to their satisfaction, the user causes the client program 150to send (step 692) the update requests to the server program 250 byactivating button element 352. Upon receipt by the server program 250,the client program 150 causes the appropriate addressee records to betagged as “requested” (step 690).

Processing Update Requests. FIG. 7:

Steps 705 & 710: Server program 250 receives current update requestsfrom the client program 150 and records (step 710) the addresseeidentifiers 308 (i.e. first and last name and email address) and thecorresponding URN email text 344 for each addressee.

Steps 712-732: Server program 250 compares current addressee identifiers308 with information contained in the Tags master file 255. Currentaddressees with a status tag of status “blocked” are tagged as “blocked”in the status tag file 160.2 on the client computer 100 and a notice ofpending update 177 is prepared (step 760) for later delivery to thesender (step 1010). The server program compares current addresseeidentifiers 308 with information in the Update Request master file 261.If the “multiple-requests” threshold (step 715) has been exceeded, thenthe server program stores the update request from the sender and“bundles” the sender's URN email together with other senders' URN emailsfor delivery as one email at a later time. The multiple-requeststhreshold is a counting function of the server program 250 whichincrements by one each time a URN email 314 is received by the serverprogram 250 addressed to a single addressee within a certain timewindow. For example, if the multi-request threshold is set to three andthe time window is set to 24 hours then the server program will begin tosave up (bundle) URN emails for that particular addressee upon receiptof the 4^(th) URN email and any subsequent URN emails received by theserver program within 24 hours of the previous delivery of URN emails tothe addressee. When the time window expires, the server program's emailmanager 260 forwards (step 730) to the addressee one single URN emailcontaining a listing of all the individual URN emails and theirrespective senders and initializes the Response Threshold clock 176(step 732) and sets a “pending” tag (step 755) for the addressee andeach sender. If the multi-request threshold (step 715) has not beenexceeded, then the email manager 260 forwards (step 725) the URNemail(s) 314 from each sender to the appropriate addressees and starts(i.e. initializes) the Response Threshold clock 176 (step 732) and setsthe status tag in the tags master file 255 to a status of “pending” foreach addressee and sender combination.

Steps 735-765: All sent URN emails are tagged as “pending” (step 755)until such time as they are tagged with a different status tag. Emailmanager 260 records statistics in the statistics file 264.10 such as thedate, time and email address of every URN email sent.

Email manager 260 “listens” for responses to sent URN emails. Responsesthat indicate that an email is “undeliverable” (step 735) are tagged as“undeliverable” (step 740) and a notice of pending update 177 (FIG. 2-B)(step 760) is prepared for later delivery (step 1010). The serverprogram communicates pending updates and status updates (step 960) tothe client program on a periodic basis (typically daily). If a responsefrom the addressee is not received by the email manager 260 by the timethe Response Threshold (determined by Response Threshold clock 176) hasbeen reached, then the addressee is considered non-responsive and a “noresponse” tag is activated (step 750) for that addressee and thecorresponding sender (user) and the Response Threshold clock for theaddressee is reset to zero.

Steps 805-820 (FIG. 8): Addressee processes: Addressee receives andopens the URN email and clicks on text element 346 contained in the URNemail 314. The URL contained in the text element 346 when entered into aweb browser will cause the web browser to display to the recipient theAddressee Validation form (FIG. 3-C).

Update Processing:

Steps 910-925: In the representative embodiment of the system, theAddressee Validation form (FIG. 3-C) is a web page and is “served” (asis well known in the art) by the server program 250. AddresseeValidation form FIG. 3-C contains a text element 395 which displays theidentification information 308 of the intended recipient (addressee). Ifthe recipient is not the intended recipient they will select “NO” buttonelement 397. Activating “NO” button element 397 will cause the serverprogram to tag the recipient (step 920) as “not intended recipient” andprepare a “notice of pending update” (step 985) for later delivery tothe sender (step 1010). If recipient activates “YES” button element 396,then the server program 250 will display (step 925) update screen FIG.3-D.

FIG. 3-D: In the representative embodiment of the system, the UpdateForm 360 (FIG. 3-D) is a web page and is “served” (as is well known inthe art) by the server program 250. Update form 360 contains a textelement 363. The text element 363 typically displays a greeting message,but can display any type of information such as, for example,instructions. When activated, help button element 362 displaysadditional instructions. Sender identification element 364 displaysidentification information about the sender, thus allowing the recipientto confirm the identity of the sender of the URN email. A currentlyactive visual element 365 is a visual element such as, for example,color, shading, or pattern which identifies the “currently active”sender 370. Sender information element 370 displays identificationinformation such as, for example, first and last names, email address,company name, etc. about the currently active sender. Additional senderinformation elements 376 display identification information aboutadditional senders (step 330). The additional sender informationelements 376 can display identification information for a multiplicityof additional senders. Additional sender information elements 376 can beviewed by the addressee by manipulating slide element 378. A differentcurrently active sender is activated by the user by, for example,clicking on one of the multiplicity of elements 376. Content displayelements 366, 367, 368 and 369 display existing content 172. Existingcontent 172 is the content related to the addressee which is currentlystored in the user's (sender's) address book 170. Display element 366displays addressee identification information 308 and is editable by therecipient. Element 367 displays a listing of one or more “senders” (i.e.users sending Update Request Notifications to the addressee) (steps 325or 330). A response matrix element 371 allows the addressee to selectamong multiple response elements 372, 373, 374 and 375. The addresseeactivates and deactivates response elements 372, 373, 374 and 375 by,for example, clicking on them (as is well known in the art). Activatingan occurrence of response element 372, 373, 374 or 375 produces a visualconfirmation such as, for example, a “check mark” for that occurrence ofthat element. The addressee can deactivate an occurrence of a responseelement by clicking on it again which removes the visual confirmingcheck mark. Activation of an occurrence of a response element 372adjacent to a sender identifier 370 or additional sender 376 will resultin an approved Update Request (step 950) for the associated sender 370or additional sender 376. Activation of an occurrence of a responseelement 373 adjacent to a sender identifier 370 or additional sender 376will result in a reciprocal Update Request (step 930) from the addresseeto the associated sender 370 or additional sender 376 (i.e. theaddressee is requesting that the sender provide the addressee withupdated content). Activation of an occurrence of a response element 374adjacent to a sender identifier 370 or an additional sender 376 willresult in a denied Update Request (step 930) for the associated sender370 or additional sender 376. Activation of an occurrence of a responseelement 375 adjacent to a sender identifier 370 or an additional sender376 will result in blocked Update Requests (step 940) for all futuresenders.

Element 368 displays a first grouping of existing content 172 from theaddress book 170 of the currently active (as identified by element 365)sender 364. Element 369 displays an additional grouping of existingcontent 172 from the currently active sender. Update form 360 is capableof displaying a multiplicity of existing-content groupings. Additionalcontent groupings can be viewed by manipulating slide element 377.Existing-content groupings typically group related elements of existingcontent such as, for example, “business” related contact information or“personal” contact information as depicted in the sample Update form(FIG. 3-D). Elements 366, 368 and 369 are editable by the user.

Steps 930-960 Update Processing:

If the user activates an occurrence of a response element 373 adjacentto a sender identifier 370 or additional sender 376, a reciprocal UpdateRequest (step 930) will be generated from the addressee to theassociated sender 370 or additional sender 376 if the addressee iscurrently a registered user of the client program 150. If the addresseeis not currently a registered user then the addressee will be directedthrough the registration process (FIG. 4) prior to a Reciprocal UpdateRequest (step 945) being generated. Addressees can deny a sender'supdate request (step 950) by activating an occurrence of a responseelement 374 adjacent to a sender identifier 370 or additional sender376. Addressees can block all further update requests from all futuresenders by activating an occurrence of a response element 375 adjacentto a sender identifier 370 or additional sender 376. Addressees canupdate existing content (step 970) by editing fields present withinexisting-content elements 366, 368 and 369 by selecting the desiredfield and entering changed content. Addressees approve delivery ofupdated content 174 to senders by activating an occurrence of a responseelement 372 adjacent to a sender identifier 370 or additional sender376. Addressees cause updated content 174 and current update requestresponses to be stored (step 975) on server system 130, Responsethreshold to be reset to zero (step 980) and notices of pending updates177 to be prepared (step 985) by activating button element 379.

Steps 1005-1035, Client Program Update Processing:

Server program 250 sends notifications of “pending updates” to senderson a periodic basis. The frequency of such periodic notifications isdetermined by a timing function such as, for example, Pending-Updatesthreshold clock 178. The frequency of update notifications is infinitelyvariable. Pending updates notification is not required for properfunctioning of the system as the representative embodiment of the systemprovides for automatic execution of frequent communications betweenclient program 150 and server program 250 during which updates aretransacted. Client program 150 establishes a communication session withthe server program 250 and requests updated content 174 (step 1015).Server program 250 passes to the client program updated content 174 aswell as status tags 255 and, when applicable, statistics 264.10, eventinformation 264.8, log information and client program updates 256.2.2 aswell as other appropriate information necessary for the proper operationof the system. Client program 150 communicates with address book 170(step 1020) via address book interface 160 and updates addressee records171 in address book 170 (step 1025) with updated content 174. To providefor maximum flexibility, it is advantageous that the re-system providefor storage and retrieval of updated content and existing content onboth the client computer as well as on the server system. As such, therepresentative embodiment of the system provides for storage andretrieval of updated content and existing content on both the clientcomputer 100 and the server system 130. The system allows that addresseerecords may have portions of updated and/or existing content stored onboth the client computer 100 and the server system 130, even if thecontent makes up just one addressee record. For example, the user mayelect to store first name, last name and phone number information on awireless telephone embodiment of the client computer 100 and associatedadditional content such as, for example, address, company, etc. on theserver system 130. Client program 150 updates status tags 160.2 foraddressee records 171 containing updated content with a status tag of“updated”. Client program 150 also updates or applies (step 1035) otherstatus tags to addressee records as appropriate such as, for example,“denied”, “blocked”, “undeliverable”, “pending”, etc. Status tags 160.2and 255 each include a date and time stamp indicating when the statustag was updated.

What is claimed is:
 1. A system for contact information management,comprising: a memory comprising an address book data structure of anaddress book; a display screen comprising a user interface thatdisplays, to a sender, identifying information of an addresseeassociated with an addressee computer, which identifying information isfrom existing contact information of the addressee extracted from theaddress book data structure of the address book in the memory; and acomputer processor operatively coupled to the display screen and thememory, wherein the computer processor: transmits, over a network, arequest for an update to the existing contact information of theaddressee to the addressee computer, which request is transmitted to theaddressee computer through a computer server; receives, over thenetwork, updated contact information of the addressee from the addresseecomputer through the computer server; and updates the address book datastructure in the memory with the updated contact information of theaddressee.
 2. The system of claim 1, wherein the user interfacecomprises one or more user interface elements that permit the sender toinput the request for the update to the existing contact information ofthe addressee.
 3. The system of claim 2, wherein the one or more userinterface elements permit the sender to input a request for an update toexisting contact information of another addressee.
 4. The system ofclaim 2, wherein the one or more user interface elements permit thesender to format and manage the request for the update.
 5. The system ofclaim 2, wherein the one or more user interface elements permit thesender to select the addressee from a plurality of addressees.
 6. Thesystem of claim 1, wherein the user interface comprises a status screendisplaying a status of the request for the update.
 7. The system ofclaim 6, wherein the status corresponds to a pending or a deniedrequest.
 8. The system of claim 1, wherein the display screen andcomputer processor are included in a sender computer of the sender. 9.The system of claim 1, wherein the computer processor transmits therequest for the update upon receiving input for the request from thesender on the user interface.
 10. The system of claim 1, wherein thecomputer processor extracts the existing contact information of theaddressee from the address book data structure of the address book inthe memory operatively coupled to the computer processor.
 11. A systemfor contact information management, comprising: a display screencomprising a user interface that displays, to an addressee, identifyinginformation of a sender associated with a sender computer and existingcontact information of the addressee extracted from an address book datastructure of an address book in memory on the sender computer; and acomputer processor operatively coupled to the display screen, whereinthe computer processor: receives, over a network, a request for anupdate to the existing contact information of the addressee from thesender computer, which request is received through a computer server;and retrieves the updated contact information of the addressee frommemory; and transmits, over the network, the updated contact informationof the addressee to the sender computer, which updated contactinformation is transmitted through the computer server.
 12. The systemof claim 11, wherein the user interface comprises one or more userinterface elements that permit the addressee to view the identifyinginformation of the sender.
 13. The system of claim 11, wherein the userinterface comprises one or more user interface elements that permit theaddressee to update the existing contact information.
 14. The system ofclaim 11, wherein the user interface comprises one or more userinterface elements that permit the addressee to request contactinformation from the sender.
 15. The system of claim 11, wherein theuser interface comprises one or more user interface elements that permitthe addressee to approve or deny the request.
 16. The system of claim11, wherein the display screen and computer processor are included in anaddressee computer of the addressee.
 17. The system of claim 11, whereinthe identifying information of the sender includes a sender identifier.18. The system of claim 17, wherein the computer processor performs alook up of the sender identifier in a database prior to transmitting theupdated contact information of the addressee to the sender computer. 19.The system of claim 18, wherein the database is a remote databaseaccessible over the network.